home *** CD-ROM | disk | FTP | other *** search
- Path: ix.netcom.com!netnews
- From: JEThomas@ix.netcom.com (Jonah Thomas)
- Newsgroups: comp.object,comp.software-eng,comp.lang.c++
- Subject: Re: Moving from C to C++
- Date: 31 Jan 1996 23:34:33 GMT
- Organization: Netcom
- Message-ID: <4eoua9$pe4@cloner4.netcom.com>
- References: <4cs44p$3pk@ixnews8.ix.netcom.com> <4dk8ts$fpc@antares.en.com> <4enr8i$t8n@mrnews.mro.dec.com>
- NNTP-Posting-Host: ix-dc6-07.ix.netcom.com
- X-NETCOM-Date: Wed Jan 31 3:34:33 PM PST 1996
-
- In <4enr8i$t8n@mrnews.mro.dec.com> rkielty@drlove.ilo.dec.com (Robert Kielty)
- writes:
-
- >In article <JSA.96Jan29134029@organon.com>,
- > jsa@organon.com (Jon S Anthony) writes:
-
- >>Where's the ":-)"? I get a contract on day x and day x+10 I have a wodge
- >>of C++ "coders" hacking out the "program". That sounds about like what one
- >>would expect from the infamous "C/C++ mentality". 1/2 :-)
-
- >Good point, I think Jonah did really well to interview 250 people,
- >make 250 job offers, and proccess the acceptances and get all the
- >office space and hardware sorted (remember thats 250 desks and
- >workstations) in ten days! Somebody call Guinness! Fair play to ye!
-
- I'm speaking strictly from rumor and hearsay, and not at all from my
- experience. Rumor has it that there have been times when the federal
- government, in its downsizing, has contracted out sizable software
- work. Nobody knew who'd get the contract until it was announced, so it
- would be expensive to keep a large crew standing by in case you got it.
- The payment was partly in terms of programmer hours + overhead. If you
- proposed to use 300 coders instead of 250 then you'd be less likely to
- get the contract, and if you took a month to hire your coders then your
- revenue the first quarter would be drastically reduced. So it made a
- certain sense to trust some reliable headhunter to do the hiring quick,
- and it was worth a premium to get the physical plant settled quickly.
- And within reason the contract would pay those premiums.
-
- For all I know those days are gone, if they ever were. The federal government
- may have decided that this approach to contracting produces inadequate
- results. But my point was that when you need a lot of people fast, you take
- what you can get. And what you can get is C/C++
-
- >In fairness, Jonah's point is valid minus the hyperbole.
- >In choosing any one technology over another one must
- >consider the availability of people who can handle the
- >technology.
-
- Yes, that's it!
-
- Last month I talked with a COBOL programmer. He'd been working for the
- government and got laid off last year. He started to learn C++ and
- didn't like it -- too tricky, too hard to keep track. Now he has a
- COBOL job with a company that subcontracted from a second company that
- subcontracted from a third company that subcontracted from the company that
- won the contract. The software handles transactions that involve over a dozen
- different federal agencies. It turns out that it's the "same" software that
- he helped write 17 years ago, his second federal project. He said that nobody
- noticed it in his records and his supervisor was surprised to hear it. (The
- code has had 17 years of maintenance since those days, of course.) Suppose
- that 17 years ago they'd decided to use some better language than COBOL.
- SNOBOL or whatever. How likely is it that they could keep it going this long,
- handing it off to subcontractors? COBOL was the best language then because it
- was the language they could count on for Off-The-Shelf coders. Now C/C++ is
- the best language because it's the one that has plenty of coders on the shelf.
-
-